computer-implemented method of a relay for cross-chain interactions in a unified trusted protocol ne

专利摘要:
Embodiments of the present invention include identifying through a relay that is communicatively connected to a first trust protocol instance and a second trust protocol instance in a trust protocol network. unified, a trust protocol domain name of a first trust protocol instance; identifying a trust protocol domain name from the second trust protocol instance; receiving, from a node of the first trust protocol instance, an access request to access the second trust protocol instance, wherein the access request includes the trust protocol domain name of the second trust protocol instance; identify a second trust protocol instance string identifier based on the second trust protocol instance trust protocol domain name, where the second trust protocol instance string identifier indicates a protocol network configuration trust of the second instance of trust protocol; and providing access to the second trust protocol instance to the first trust protocol instance based on the trust protocol network configuration indicated by the string identifier of the second trust protocol instance.
公开号:BR112019007991A2
申请号:R112019007991
申请日:2018-11-16
公开日:2019-09-10
发明作者:Qiu Honglin
申请人:Alibaba Group Holding Ltd；
IPC主号:

专利说明:

“COMPUTER IMPLEMENTED METHOD OF A RELAY FOR CROSS-CHAIN INTERACTIONS IN A UNIFIED CONFIDENCE PROTOCOL NETWORK, COMPUTER-READABLE, NON-TRANSITIONAL AND SYSTEM STORAGE” Field of the Invention [001] The present invention relates to an implemented method by computer from a relay for cross-chain interactions in a unified trust protocol network, to a computer-readable, non-transitory storage medium and to a system.
Background of the Invention [002] Distributed accounting systems (DLSs), which can also be called consensus networks and / or trust protocol networks (blockchain), allow participating entities to store data in a secure and immutable way. DLSs are commonly referred to as trust protocol networks without referring to any particular user case (for example, cryptocurrencies). Examples of types of trust networks can include public trust networks, private trust networks and consortium trust networks. A public trust protocol network is open for all entities to use DLS and participate in the consensus process. A private trusted protocol network is provided for a specific entity, which centrally controls read and write permissions. A consortium trust protocol network is provided for a select group of entities, which control the consensus process and include an access control layer.
[003] Trust protocols are used in cryptocurrency networks, which allow participants to make transactions to buy / sell goods and / or services using a cryptocurrency. An
Petition 870190056948, of 6/19/2019, p. 9/66
2/44 common cryptocurrency includes Bitcoin. In cryptocurrency networks, record-keeping models are used to record transactions between users. Examples of record-keeping models include an unused transaction exit model (UTXO), and the account model (also referred to as an account-based model or an account / balance model).
Description of the Invention [004] Embodiments of the present invention include computer-implemented methods for a domain name scheme for trusted protocol systems. More particularly, the embodiments of the present invention address cross-chain interactions using a unified domain name scheme in block chain systems.
[005] In some embodiments, actions include identifying, through the relay, which is communicatively linked to a first trust protocol instance and a second trust protocol instance in the unified trust protocol network, a trust protocol domain name of a first trust protocol instance, where the trust protocol domain name of the first trust protocol instance is a unique identifier of the first trust instance and matches uniquely a chain identifier of the first trust instance in the unified trust network; identify, through the relay, a trust protocol domain name of the second trust protocol instance, where the trust protocol domain name of the second trust protocol instance is a unique identifier of the second trust protocol instance and uniquely matches a chain identifier of the second trust protocol instance in the unified trust network; receive, through the relay from a node
Petition 870190056948, of 6/19/2019, p. 10/66
3/44 of the first trust protocol instance, an access request to access the second trust protocol instance, where the access request comprises the trust protocol domain name of the second trust protocol instance; identify, through the relay, the chain identifier of the second trust protocol instance based on the domain name of the trust protocol of the second trust protocol instance, where the chain identifier of the second trust protocol instance indicates a trust protocol network configuration of the second trust protocol instance; and providing, through the relay, access to the second trust protocol instance for the first trust protocol instance based on the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance.
[006] Other embodiments include corresponding systems, devices and computer programs, configured to perform the actions of the encrypted methods on computer storage devices.
[007] These and other embodiments may optionally include one or more of the following characteristics:
[008] A first resource, combinable with any of the following resources, in which the identification of a trust protocol domain name of the first trust protocol instance includes the use of the trust protocol domain name of the first instance of trust trust protocol as a local identifier of the first trust protocol instance; and the identification of a trust protocol domain name of the second trust protocol instance comprises the use of the trust protocol domain name of the second trust protocol instance as a local identifier of the second trust instance
Petition 870190056948, of 6/19/2019, p. 11/66
4/44 trust protocol.
[009] A second resource, combinable with any of the following resources, in which to identify the chain identifier of the second trust protocol instance based on the trust protocol domain name of the second trust protocol instance comprises identifying the identifier string of the second trust protocol instance according to query information stored locally in the relay based on the domain name of the trust protocol.
[010] A third resource, combinable with any of the following resources, in which to identify the second identifier of the trust protocol string based on the domain name of the second trust of the trust protocol comprises identifying the identifier second trust chain string based on the second trust protocol instance trust name from a remote unified trust domain name server.
[011] A fourth resource, combinable with any of the following resources, in which the provision, through the relay, of access to the second trust protocol instance for the first trust protocol instance based on the security protocol network configuration trust indicated by the chain identifier of the second trust protocol instance comprises providing, through the relay, access to the second trust protocol instance for the first trust protocol instance via a second relay; wherein the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance is identified by the second relay based on the same chain identifier as the second trust protocol instance; and where the second instance of the trust protocol is accessed
Petition 870190056948, of 6/19/2019, p. 12/66
5/44 by the second relay based on the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance.
[012] A fifth resource, combinable with any of the following resources, in which the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance is identified by the second relay according to the stored search information locally on the second relay based on the same chain identifier as the second trust protocol instance.
[013] A sixth resource, combinable with any of the following resources, in which the trust network configuration indicated by the chain identifier of the second trust protocol instance is identified by the second relay based on the protocol domain name of the second trust protocol instance from a remote unified trust domain name server.
[014] A seventh resource, combinable with any of the following resources, the domain name of the trust protocol of the first instance of trust protocol comprises a first human-readable marker; and the trust protocol domain name of the second trust protocol instance comprises a second human-readable marker.
[015] The present invention also provides one or more computer-readable storage media coupled to one or more processors and having instructions stored on it that, when executed by one or more processors, cause the one or more processors to perform operations according to embodiments of the methods provided here.
Petition 870190056948, of 6/19/2019, p. 13/66
6/44 [016] The present invention further provides a system for implementing the methods provided herein. The system includes one or more processors, and a computer-readable storage medium coupled to one or more processors with instructions stored on it that, when executed by one or more processors, cause one or more processors to perform operations according to ways carrying out the methods provided here.
[017] It is understood that the methods according to the present invention can include any combination of the aspects and characteristics described herein. That is, the methods according to the present invention are not limited to the combinations of aspects and characteristics specifically described herein, but also include any combination of the aspects and characteristics provided.
[018] Details of one or more embodiments of the present invention are presented in the accompanying drawings and in the description below. Other features and advantages of the present invention will be apparent from the description and drawings, and from the claims.
Brief Description of the Drawings [019] Figure 1 illustrates an example of an environment that can be used to carry out embodiments of the present invention.
[020] Figure 2 illustrates an example of conceptual architecture according to embodiments of the present invention.
[021] Figure 3 illustrates an example of a unified trust protocol (UBCDN) domain name of a trust protocol instance, according to embodiments of the present invention.
[022] Figure 4 illustrates an example of a UBCDN management scheme in a unified trust protocol network, according to embodiments of the present invention.
Petition 870190056948, of 6/19/2019, p. 14/66
7/44 [023] Figure 5 illustrates an example of a process for using a trust protocol domain name from a trust protocol instance for cross-chain interactions in a unified trust network, according to forms of trust. realization of the present invention.
[024] Figure 6 illustrates an example of a process for authenticating a UBCDN from a trusted protocol instance, according to embodiments of the present invention.
[025] Figure 7 describes an example process of a UBCDN owner of a trust protocol instance (a UBCDN owner), according to embodiments of the present invention.
[026] Figure 8 illustrates an example of a relay process for cross-chain interactions in a unified trust protocol network, according to embodiments of the present invention.
[027] Similar reference symbols in the various drawings indicate similar elements.
Description of Embodiments of the Invention [028] Embodiments of the present invention include computer-implemented methods for a domain name scheme for trusted protocol systems. More particularly, the embodiments of the present invention relate to cross-chain interactions using a unified domain name scheme in trusted protocol systems.
[029] In some embodiments, actions include identifying, through the relay that is communicatively linked to a first instance of trust protocol and a second instance of trust protocol in the unified trust network, a name of protocol trust domain of a first protocol instance
Petition 870190056948, of 6/19/2019, p. 15/66
8/44 trust, where the trust protocol domain name of the first trust protocol instance is a unique identifier of the first trust protocol instance and uniquely corresponds to a chain identifier of the first trust protocol instance trust in the unified trust protocol network; identify, through the relay, a trust protocol domain name of the second trust protocol instance, where the trust protocol domain name of the second trust protocol instance is a unique identifier of the second trust protocol instance and uniquely matches a chain identifier of the second trust protocol instance in the unified trust network; receive, through the relay from a node of the first trust protocol instance, an access request to access the second trust protocol instance, where the access request comprises the domain name of the second trust trust protocol trust protocol; identify, through the relay, the chain identifier of the second trust protocol instance based on the domain name of the trust protocol of the second trust protocol instance, where the chain identifier of the second trust protocol instance indicates a trust protocol network configuration of the second trust protocol instance; and providing, through the relay, access to the second trust protocol instance for the first trust protocol instance based on the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance.
[030] To provide an additional context for embodiments of the present invention, and as introduced above, distributed accounting systems (DLSs), which can also be referred to as consensus networks (for example, constituted by peer-to-peef nodes ), and
Petition 870190056948, of 6/19/2019, p. 16/66
9/44 trust protocol, allows participating entities to conduct transactions securely and immutably and store data. Although the term trust protocol is generally associated with the Bitcoin cryptocurrency network, the trust protocol is used here to generally refer to a DLS without reference to any particular use case. As introduced above, a trust protocol network can be provided as a public trust protocol network, a private trust protocol network, or a consortium trust network.
[031] In a public trust protocol network, the consensus process is controlled by nodes in the consensus network. For example, hundreds, thousands, even millions of entities can cooperate in a public trust protocol network, each of which operates at least one node in the public trust protocol network. Thus, the public trust protocol network can be considered a public network in relation to the participating entities. In some examples, most entities (nodes) must sign each block in order for the block to be valid, and added to the trust protocol (distributed accounting) of the trust protocol network. An example of a public trust protocol network includes the Bitcoin network, which is a peer-to-peer payment network. The Bitcoin network uses distributed accounting, known as a trust protocol. As noted above, the term trust protocol, however, is used to generally refer to distributed accounts with no particular reference to the Bitcoin network.
[032] In general, a public trust protocol network supports public transactions. A public transaction is shared with all nodes within the public trust protocol network and is stored in a global trust protocol. A global trust protocol is a trust protocol that is replicated on all nodes. That is, all nodes
Petition 870190056948, of 6/19/2019, p. 17/66
10/44 are in a perfect state of consensus regarding the global trust protocol. To reach consensus (for example, agreeing to add a block to a trust protocol), a consensus protocol is implemented within the public trust protocol network. An example of a consensus protocol includes, without limitation, proof of work (POW) implemented in the Bitcoin network.
[033] In general, a private trusted protocol network is provided for a particular entity, which centrally controls read and write permissions. The entity controls which nodes are able to participate in the trust protocol network. Consequently, private trust protocol networks are generally referred to as allowed networks that place restrictions on who is allowed to participate in the network, and on their level of participation (for example, only in certain transactions). Various types of access control mechanisms can be used (for example, existing participants vote to add new entities, a regulatory authority can control admission).
[034] In general, a consortium trust protocol network is private between participating entities. In a consortium trust protocol network, the consensus process is controlled by an authorized set of nodes, one or more nodes being operated by a respective entity (for example, a financial institution, insurance company). For example, a consortium of ten (10) entities (for example, a financial institution, insurance company) may operate a consortium trust protocol network, one operating at least one node in the consortium trust protocol network. In this sense, the consortium trust protocol network can be considered a private network in relation to the participating entities. In some examples, each entity (node) must sign all blocks for the block to be valid and added to the trust protocol. In
Petition 870190056948, of 6/19/2019, p. 18/66
11/44 some examples, at least a subset of entities (nodes) (for example, at least 7 entities) must sign all blocks for the block to be valid and added to the trust protocol.
[035] Embodiments of the present invention are described in more detail herein with reference to a consortium trust protocol network. It is contemplated, however, that the embodiments of the present invention can be carried out in any appropriate type of trust protocol network.
[036] The embodiments of the present invention are described here in greater detail in view of the above context. More particularly, and as shown above, the embodiments of the present invention are intended for a domain name scheme for cross-chain interactions in trusted protocol systems.
[037] Various trust protocol platforms, environments or products have been developed based on different trust protocol technologies. Examples of trust protocol products include Ethereum and Bitcoin. The current trust protocol network includes multiple trust protocol instances deployed based on the different trust protocol products. For example, the current trust protocol network includes multiple instances of trust protocol such as public trust protocols, private trust protocols, or consortium trust protocols that are developed based on Ethereum or Bitcoin technologies.
[038] The current access mode of each trust protocol instance requires access from a client node (also called a client terminal) of the trust protocol or its technical components, such as SDKs. To connect accurately to a specific trust protocol instance, the customer needs to load their
Petition 870190056948, of 6/19/2019, p. 19/66
12/44 trust protocol network. These trust protocol network settings are typically hash, member certificates, etc. These configurations are unreadable for humans and it is difficult to identify which chains the configurations identify.
[039] The present invention provides a domain name scheme for the trust protocol network. Specifically, a unified trust domain (UBCDN) domain name is provided to serve as a unique identifier for each trust protocol instance (also referred to as a trust network or chain case) in the trust network . A trust protocol instance can be, for example, a form or practice of a trust protocol based on a trust protocol or technology platform (for example, Ethereum). Each UBCDN uniquely links a domain name of a trust protocol instance (also known as a trust protocol domain name) with a corresponding network configuration of the trust protocol instance (also referred to as a protocol network configuration reliable). In some embodiments, the trust protocol network configuration can be represented or indicated by a string identifier. A client node of a trust protocol instance can obtain a corresponding trust network configuration by analyzing the UBCDN to identify the chain identifier. Based on the configuration of the trust protocol network, the client node can connect to, or otherwise access, the specific trust protocol instance.
[040] The domain name scheme described can provide a unified protocol for interactions between trust protocol systems in a unified (or global) trust protocol network that includes multiple or all deployed trust protocol instances, with
Petition 870190056948, of 6/19/2019, p. 20/66
13/44 based on different trusted protocol products or technologies. All trust instances in the unified trust network follow the same domain name scheme and are assigned unique UBCDNs. In some embodiments, each trust protocol instance in the unified trust network is assigned a single UBCDN that can be recognized by all trust protocol instances in the unified trust network, regardless of different platforms, technologies , or relays that are used in the unified trust protocol network. In some embodiments, the UBCDN defines a domain of administrative autonomy, authority or control of a trust protocol instance within the unified trust protocol network. In some embodiments, the unified trust protocol network can be considered as a counterpart of the Internet to the IP network, while the UBCDN can be considered as a domain name mapping of an IP resource on the IP network with a IP address of the IP Resource.
[041] Each trust protocol instance in the unified trust protocol network can be uniquely identified by a corresponding UBCDN, in order to facilitate multiple or cross-chain communications. For example, unlike existing cross-chain embodiments like COSMOS, which uses a relay chain for cross-chain interactions, in which each trust protocol is assigned an identifier (ID) within the relay chain network, but the ID is only local in scope and cannot be reused in other relay chain networks, in the domain name scheme described, the UBCDN can be used and is globally recognized by all trusted protocol instances in the protocol network unified trust, despite how many relay chains are included in the unified trust protocol network.
Petition 870190056948, of 6/19/2019, p. 21/66
14/44 [042] In addition, the domain name scheme described simplifies the identification or addressing protocol for cross-chain interactions in trust protocol systems. For example, in the domain name scheme described, a single UBCDN is sufficient to uniquely identify a trust instance and is globally recognizable by all trust protocol instances in the unified trust network for interactions between different trust protocol networks, whereas in COSMOS a trust protocol instance is assigned multiple different IDs when the trust protocol instance associates with multiple relay chains for the trust protocol instance to interact with other trust protocols.
[043] In addition, the UBCDN can include a human-readable identifier or marker, helping users to easily memorize and reach a trust protocol instance, and thus promote the adoption or use of the trust protocol instance. For example, operators or owners of public trust protocols, private trust protocols or consortium trust protocols can choose trust protocol domain names that match their names, helping users to remember the identifiers of trust instances , and it also facilitates the translation, resolution, or other identification of the chain identifiers corresponding to the domain names of the trust protocol, accelerating cross-chain interactions in the unified trust protocol network.
[044] In addition to providing easily recognizable and memorable names to identify trust protocol instances, UBCDN allows a trust protocol instance to keep its trust domain name even though the network configuration
Petition 870190056948, of 6/19/2019, p. 22/66
15/44 underlying the trust protocol instance is changed (for example, by system update or move or migration to a different physical location in the network address topology). In the event of such a change or update, the chain identifier of the trust instance can be changed while the domain name of the trust protocol can remain the same. The UBCDN owner can change the mapping of the trust protocol domain name to the updated chain identifier and allow others (for example, other trust protocol instances or client nodes) to use the same trust protocol domain name for refer to and access the trust protocol instance.
[045] Figure 1 represents an example of an environment (100) that can be used to carry out embodiments of the present invention. In some examples, the sample environment (100) allows entities to participate in a consortium trust protocol network (102). The example environment (100) includes computing systems or devices (106, 108) and a network (110). In some examples, the network (110) includes a local area network (LAN), wide area network (WAN), the Internet or a combination of them, and connects web sites, user devices (for example, computing devices ) and backend system. In some examples, the network (110) can be accessed via a wired and / or wireless communication link.
[046] In the example described, the computing systems (106, 108) can include any appropriate computing system that allows participation as a node in the consortium trust protocol network (102). Examples of computing devices include, without limitation, a server, a desktop computer, a laptop computer, a tablet computer device and a smartphone. In some examples, computing systems (106, 108) host one or more services implemented per computer
Petition 870190056948, of 6/19/2019, p. 23/66
16/44 to interact with the consortium trust protocol network (102). For example, the computing system (106) can host computer-implemented services from a first entity (for example, user A), such as a transaction management system that the first entity uses to manage its transactions with one or more entities ( for example, other users). The computing system (108) can host computer-implemented services from a second entity (for example, user B), such as a transaction management system that the second entity uses to manage its transactions with one or more other entities (for example , other users). In the example in Figure 1, the consortium trust protocol network (102) is represented as a peer-to-peer network of nodes, and the computing systems (106, 108) provide nodes of the first entity and second entity, respectively , who participate in the consortium trust protocol network (102).
[047] Figure 2 illustrates an example of conceptual architecture (200) according to embodiments of the present invention. The exemplary conceptual architecture (200) includes an entity layer (202), a hosted services layer (204) and a trust protocol network layer (206). In the example shown, the entity layer (202) includes three entities, Entity_1 (E1), Entity_2 (E2) and Entity_3 (E3), each entity having a respective transaction management system (208).
[048] In the example described, the hosted services layer (204) includes interfaces (210) for each transaction management system (208). In some examples, a respective transaction management system (208) communicates with a respective interface (210) over a network (for example, the network (110) in Figure 1) using a protocol (for example, data transfer protocol) secure hypertext (HTTPS)). In some examples, each interface (210) provides a communication connection between a
Petition 870190056948, of 6/19/2019, p. 24/66
17/44 the respective transaction management system (208), and the trust protocol network layer (206). More particularly, the interface (210) communicates with a trust protocol network (212) of the trust protocol layer (206). In some examples, communication between an interface (210) and the trust protocol network layer (206) is conducted using remote procedure calls (RPCs). In some examples, interfaces (210) "host" the trust protocol network nodes for the respective transaction management systems (208). For example, interfaces (210) provide the application programming interface (API) for accessing the trusted protocol network (212).
[049] As described here, the trust protocol network (212) is provided as a peer-to-peer network including a number of nodes (214) that record information immutably in a trust protocol (216). Although a single trust protocol (216) is schematically represented, several copies of the trust protocol (216) are provided, and are maintained through the trust protocol network (212). For example, each node (214) stores a copy of the trust protocol. In some embodiments, the trust protocol (216) stores information associated with transactions that are carried out between two or more entities that participate in the consortium trust protocol network.
[050] Figure 3 illustrates an example of a unified trust protocol (UBCDN) domain name (300) of a trust protocol instance, according to embodiments of the present invention. The UBCDN (300) may include a trust protocol domain name (310) and a corresponding string identifier (320) of the trust instance. The domain name of the trust protocol (310) can be human-readable. The string identifier (320) can indicate a trusted protocol network configuration of the
Petition 870190056948, of 6/19/2019, p. 25/66
18/44 trust and allows access to the trust protocol instance based on the trust protocol network settings. In some embodiments, the UBCDN (300) may include additional fields or be represented as a tape or other data structure.
[051] The domain name of the trust protocol (310) can be easy to use. For example, the domain name of the trust protocol (310) can be a text-based marker that is easier to remember than the corresponding numeric string identifier (320) (for example, a 40-character hexadecimal address used in Ethereum protocols In some embodiments, the domain name of the trust protocol (310) can be represented as a tape or other data structure.
[052] In some embodiments, the domain name of the trust protocol (310) may have a defined syntax to further facilitate the understanding of the origin, ownership or organization of the underlying trust protocol instance. For example, the domain name of the trust protocol (310) can be designed similarly to the domain name on the IP network. The trust protocol domain name (310) can include one or more parts or markers. The one or more labels can be concatenated and have a hierarchy of domains descending from the label from right to left in the name. Each marker on the left specifies a subdivision or subdomain of the domain to the right. For example, a domain name from the chain's trust protocol (310). organization indicates that the underlying chain trust protocol instance is a subdomain of the organization's domain and belongs to the organization. In some embodiments, the domain name of the trust protocol (310) may define an additional or different syntax.
[053] The chain identifier (320) can include an identifier
Petition 870190056948, of 6/19/2019, p. 26/66
19/44 addressable that is used to address and access the trust instance in the trust network. The chain identifier (320) can indicate a trustee network configuration of the trustee instance and allow access to the trustee instance based on the trustee network settings. For example, multiple instances of trust protocol can be deployed based on Ethereum technology. The trust protocol instance can be, for example, a MainNet chain, a test chain, a private chain, or a consortium chain. An Ethereum customer can establish a connection with an Ethereum trust protocol instance by loading the genesis block (that is, the first block) of the Ethereum trust protocol instance. The genesis block is equivalent to a unique identifier for the Ethereum trust protocol instance. Thus, in some embodiments, one or more fields (for example, a hash value) from the genesis block of an Ethereum trust protocol instance can be extracted as the string identifier (320) of the Ethereum trust protocol instance . In some embodiments, the chain identifier of a trust protocol instance can include a hash value from a trust protocol instance genesis block, as well as a network ID that identifies the trust protocol instance. In some embodiments, the network ID allows transactions on the trust protocol instance to appear different from other chains, for example, by signing transactions differently, depending on the network ID used. As such, the network ID indicates an additional network configuration that can be used to link or otherwise access the trusted protocol instance. The chain identifier (320) can include additional or different components or fields, for example, depending on the underlying trust protocol technology or platform of the
Petition 870190056948, of 6/19/2019, p. 27/66
20/44 trust protocol.
[054] The UBCDN (300) creates a one-to-one mapping of the trust protocol domain name (310) and its corresponding string identifier (320) of the trust protocol instance. Given the domain name of the trust protocol (310), its corresponding string identifier (320) can be translated, resolved, or otherwise identified, and vice versa. As such, a node can access the trust protocol instance based on the trust protocol network configuration indicated by the chain identifier (320). As an analogy, the trust protocol domain name (310) of a trust protocol instance is similar to a domain name according to the Domain Name System (DNS) of an Internet Protocol (IP) resource ) (for example, example.com) and the string identifier (320) is similar to the IP address of the IP characteristic on the IP network.
[055] In some embodiments, for a given trust protocol domain name (310), its corresponding string identifier (320) can be translated, resolved or otherwise identified using UBCDN query information that is in cached or not stored locally, within a query computer, or remotely on the unified trust protocol network (for example, on a central UBCDN server). The UBCDN query information can include multiple UBCDN (300), each UBCDN (300) corresponding to multiple trust protocol instances. UBCDN query information can be stored, for example, in a lookup table or other data structure. The one or more nodes (for example, a client node, a consensus node, or a relay node) or a server on the unified trust protocol network can store UBCDN query information. When searching based on UBCDN query information, an identifier
Petition 870190056948, of 6/19/2019, p. 28/66
21/44 of chain (320) corresponding to a given domain name of the trust protocol (310) can be identified and vice versa.
[056] When UBCDN information is cached locally, the UBCDN query process can be faster than performing a remote UBCDN query, for example, on a remote UBCDN server. In some embodiments, at the last UBCDN remote query, a user inserts a domain name of the trust protocol (310), for example, “chain, organization” in an SDK of the user's computer device (ie, the In the client). The client node sends a request or query that includes the domain name of the trust protocol (310) “chain. organization ”to a remote UBCDN server, for example, over the Internet outside the chain. Upon receiving the request, the remote UBCDN server searches the UBCDN query information for an entry corresponding to the domain name of the trust protocol (310) “chain. organization ”and identifies the chain identifier (320) corresponding to the domain name of the trust protocol (310). Then, the remote UBCDN server responds to the client node with the chain identifier (320) corresponding to the domain name of the trust protocol (310), for example, sending a response including the corresponding chain identifier (320) to the domain name of the trust protocol (310) for the client node.
[057] Figure 4 illustrates an example of a UBCDN (400) management scheme in a unified trust protocol network, according to embodiments of the present invention. The example of the UBCDN (400) management scheme can provide improved reliability and security for UBCDN-based cross-chain communications. In some embodiments, the example UBCDN management scheme (400) has a key infrastructure
Petition 870190056948, of 6/19/2019, p. 29/66
22/44 public (PKI) to establish trust in the unified trust protocol network.
[058] For example, a certification authority (CA) (410) (for example, the PKI operator) can be used. The CA (410) issues a domain certificate (“Domain Certificate”) (420a, 420b and 420c) (collectively, domain certificate (420)) for each owner of a UBCDN (430a, 430b and 430c) (collectively , owner of UBCDN (430)). The UBCDN owner (430) can be, for example, an owner or operator of the trust protocol instance. As illustrated, the owner of UBCDN (430a) is an owner of a domain name of the trust protocol “Exemplol .chain,” the owner of UBCDN (430b) is an owner of a domain name of the trust protocol “Example2.chain ”, And the owner of UBCDN (430b) is an owner of a domain name of the trust protocol“ ExampleN.chain. ” [059] In some embodiments, the UBCDN owner (430) can obtain a domain certificate (420) by applying to the CA (410) with a certificate signing request (not shown in Figure 4). In some embodiments, the certificate request is an electronic document that contains the domain name of the trust protocol, the information from the trust protocol instance (for example, the chain identifier or other network settings), and a public key of the UBCDN owner (430). After verifying that the UBCDN owner (430) has the right to administratively manage the trust protocol domain name of the trust instance, the CA (410) can sign the request, thereby producing a public domain certificate (420). In some embodiments, the domain certificate (420) can be served to any node (for example, a client node, a consensus node or a relay node) that would like to access the instance of
Petition 870190056948, of 6/19/2019, p. 30/66
23/44 trust protocol underlying the domain name of the trust protocol (for example, “Exemplol .chain”) and proof to the node that the CA (410) trusts and issued a certificate to the UBCDN owner (430).
[060] The domain certificate (420) can include a domain name of the trust protocol (for example, “Example chain.”) And a public key of the UBCDN owner (430). The UBCDN owner (430) is the holder of the private key corresponding to the public key. The CA (410) can digitally sign the trust protocol domain name and the public key of the UBCDN owner (430) using the CA's own private key. The domain certificate (420) can include the digital signature signed by the CA (410) in the domain name of the trust protocol and the public key of the UBCDN owner (430).
[061] As described in relation to Figure 3, a UBCDN can include a domain name of the trust protocol (for example, "Example chain.") And a corresponding string identifier. The UBCDN owner (430) can publish the UBCDN and sign the UBCDN using the private key of the UBCDN owner (430). In some embodiments, the UBCDN owner (430) publishes one or more UBCDN messages (for example, UBCDN messages (440A, 450A, 440)) so that the UBCDN can be authenticated or verified.
[062] In some embodiments, UBCDN messages (440) may include UBCDN, a resulting UBCDN digital signature, and a domain certificate. The domain certificate can be the respective domain certificate (420) received from the CA (410). The UBCDN can include the domain name of the trust protocol and the chain identifier (for example, the domain name of the trust protocol (310) and the chain identifier (320), as described in relation to Figure 3). As illustrated, the UBCDN owner (430a) issues a UBCDN message (440a) that
Petition 870190056948, of 6/19/2019, p. 31/66
24/44 includes the domain name of the trust protocol (442a) “Example chain.” And a corresponding string identifier (444a) “VO chain identifier”, a digital signature (446a) and a domain certificate (448a) . The domain certificate (448a) can be the domain certificate (420a) issued by the CA (410) and received by the UBCDN owner (430a) from the CA (410). The digital signature (446a) can result from the signature of the UBCDN owner (430a) of the UBCDN (that is, the domain name of the trust protocol (442a) “Example chain” and a corresponding string identifier (444a) “Identifier String V0 ”, in this case) using the private key of the UBCDN owner (430a).
[063] Similarly, the UBCDN owner (430b) issues a UBCDN message (440b) that includes the domain name of the trust protocol (442b) “Example2.chain” and a corresponding chain identifier (444b) “Chain identifier Vx ”, a digital signature (446b) and a domain certificate (448b). The domain certificate (448b) can be the domain certificate (420b) issued by the CA (410) and received by the UBCDN owner (430b) from the CA (410). The digital signature (446a) may result from the signature of the UBCDN owner (430b) of the UBCDN (ie the domain name of the trust protocol (442b) “Example2.chain” and a corresponding chain identifier (444a) String V0 ”in this case), using the private key of the UBCDN owner (430b).
[064] In some embodiments, an authentication or verification process can be performed, for example, by any node in the unified trust protocol network or by third parties to verify the validity of a UBCDN based on the UBCDN message. This can ensure the security that is important for e-commerce, especially in connection with mobile payment transactions for cross-chain interactions in trust protocol systems.
Petition 870190056948, of 6/19/2019, p. 32/66
25/44 [065] In some embodiments, the authentication or verification process may include, for example, verifying that the domain name of the trust protocol is the same as the domain name of the trust protocol in the certificate domain; verify that the owner of UBCDN (for example, the owner of UBCDN (430a)) is the owner of the trust protocol domain name (for example, "the trust protocol domain name (442a)" Example .chain " ) by checking the digital signature on the UBCDN (for example, the digital signature (446a)) using the public key on the domain certificate (for example, the domain certificate (420a)) issued by the CA (410), and verify that the certificate domain (for example, the domain certificate (448a)) is issued by the trusted CA (410).
[066] In some embodiments, after checking the validity of the UBCDN, for example, based on the authentication or verification process, a client node can use the UBCDN for cross-chain interactions in the unified trust protocol network. For example, the client node can receive and read a UBCDN message, check the validity or legality of the UBCDN and confirm that the UBCDN is issued by the UBCDN owner; and then use the UBCDN to uniquely identify and access the trust protocol instance, for example, by identifying the string identifier corresponding to the trust protocol domain name in the UBCDN.
[067] Figure 5 illustrates an example process (500) for using a trust protocol domain name from a trust protocol instance for cross-chain interactions in a unified trust network, according to forms of trust. realization of the present invention. In some embodiments, the process example (500) can be run using one or more computer executable programs
Petition 870190056948, of 6/19/2019, p. 33/66
26/44 executed using one or more computing devices. For clarity of presentation, the following description generally describes the process (500) in the context of the other figures in this description. For example, the process example (500) can be executed by a client node of a first trust protocol instance, such as, the computing system (106) or (108) of the trust protocol network trust protocol ( 102), as described in relation to Figure 1, or the node (214) of the trust protocol network (212), as described in relation to Figure 2. However, it will be understood that the process (500) can be performed, for for example, by any suitable system, environment, software and hardware, or a combination of systems, environments, software and hardware, as appropriate. In some embodiments, several process steps (500) can be performed in parallel, in combination, in loops or in any order.
[068] In (510), a client node of a first trust instance obtains a trust protocol domain name from a different second trust instance. In some embodiments, a first trust protocol instance and the second trust protocol instance are implemented based on different trust protocol platforms. In some embodiments, a first trust protocol instance and the second trust protocol instance belong to different owners or operators. The first trust protocol example and the second trust protocol example are in a unified trust network including a number of trust protocol instances that are linked in communication by two or more relays.
[069] The trust domain name is a unique identifier of the second trust protocol instance in the unified trust network, even though the trust network
Petition 870190056948, of 6/19/2019, p. 34/66
Unified 27/44 include two or more relays. In some embodiments, each of the trust protocol instance numbers in the unified trust protocol network has only one trust protocol domain name that uniquely identifies each of the trust protocol instance numbers in the protocol network unified trust.
[070] The domain name of the trust protocol includes a human-readable marker. In some embodiments, the human-readable marker includes a text-based marker. The trust protocol domain name uniquely corresponds to a string identifier in the second trust protocol instance. The trust protocol domain name and chain identifier can be represented by a UBCDN such as UBCDN (300), as described in Figure 3. As an example, the trust protocol domain name can be the domain name of the trust protocol (310), while the chain identifier can be the corresponding chain identifier (320) in the UBCDN (300).
[071] In (520), the client node of a first trust protocol instance identifies the chain identifier of the second trust protocol instance based on the trust protocol domain name of the second trust protocol instance, where the chain identifier of the second trust instance indicates a trust network configuration of the second trust instance. In some embodiments, the chain trust of the second trust protocol instance includes a hash value from a genesis block of the second trust protocol instance and a network identifier of the second trust protocol instance, for example, as described in relation to Figure 3.
[072] In some embodiments, the identification of the chain identifier of the second trust protocol instance with
Petition 870190056948, of 6/19/2019, p. 35/66
28/44 basis on the domain name of the trust protocol includes the identification of the chain identifier of the second instance of trust protocol according to the query information stored locally on the client node based on the domain name of the trust protocol.
[073] In some embodiments, the identification of the second trust protocol string chain identifier based on the trust protocol domain name includes the identification of the second trust protocol instance string identifier from a remote unified trust domain name server based on the trust domain name. For example, the client node of a first trust protocol instance sends a request or query to the unified trust domain name server. The request includes the domain name of the trust protocol to identify the chain identifier of the second trust protocol instance. Then, the client node of a first trust protocol instance receives a response to the request from the domain name server of the unified trust protocol, where the response includes the chain identifier of the second trust protocol instance.
[074] In (530), the client node of a first trust protocol instance accesses the second trust protocol instance based on the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance. For example, a first trust protocol instance accesses the second trust protocol instance through a client node of the second trust protocol instance based on the hash value of the genesis block of the second trust protocol instance indicated by the identifier string of the second trust protocol instance. In some embodiments, a first instance of a trust protocol accesses the second
Petition 870190056948, of 6/19/2019, p. 36/66
29/44 trust protocol instance through a client node of the second trust protocol using a relay (for example, a relay node or a relay chain) or another application that is communicatively linked to a first trust protocol instance and the second instance of trust protocol.
[075] In some embodiments, to access and obtain data from the second trust protocol instance, the client node of the second trust protocol instance can configure a network configuration, such as an IP address and port number of a node (for example, a consensus node) of the second trust protocol and the hash value of the genesis block of the second trust protocol instance. The client node of the second trust instance can connect to the node of the second trust instance through the IP address and the port number of the node of the second trust instance. The client node of the second trust protocol instance can read, retrieve, download or otherwise obtain the data from the second trust protocol instance node and verify that the data obtained comes from the second trust protocol instance , for example, based on a Simple Payment Verification (SPV) protocol from the second instance of the trust protocol to determine whether the data obtained points to the hash value of the genesis block of the second instance of the trust protocol.
[076] In (540), the client node of a first trust protocol instance performs cross-chain transactions between a first trust protocol instance and the second trust protocol instance based on the domain name of the trust protocol of the second instance of trust protocol. In some embodiments, the execution of cross-chain transactions between a first trust protocol instance and the second trust protocol instance
Petition 870190056948, of 6/19/2019, p. 37/66
30/44 trust includes sending, through a first trust protocol instance, a cross-chain request that includes the trust protocol domain name from the second trust protocol instance and a data request, to a relay which is communicatively linked to a first trust protocol instance and the second trust protocol instance. The relay receives the cross-chain request and reads the trust protocol domain name from the second trust protocol instance, loads the corresponding trust protocol network configuration from the second trust instance, uses the configuration to connect to second instance of trust protocol. The relay can retrieve, download or otherwise receive the requested data from the second trust protocol instance and send the requested data to a first trust protocol instance.
[077] Figure 6 illustrates an example of process (600) for authenticating a UBCDN of a trusted protocol instance, according to embodiments of the present invention. In some embodiments, the process example (600) can be performed using one or more computer executable programs executed using one or more computing devices. For clarity of presentation, the following description generally describes the process (600) in the context of the other figures in this description. For example, the process example (600) that can be performed by the computing system (106) or (108) of the consortium trust protocol network (102), as described in relation to Figure 1, or the node (214 ) of the trust protocol network (212), as described in relation to Figure 2. However, it will be understood that the process (600) can be performed, for example, by any suitable system, environment, software and hardware, or a combination of systems, environments, software and hardware, as appropriate. In some embodiments, several steps in the process (600)
Petition 870190056948, of 6/19/2019, p. 38/66
31/44 can be performed in parallel, in combination, in loops or in any order.
[078] In (610), a computing system obtains a unified trust protocol (UBCDN) domain name message from a trust protocol instance. In some embodiments, the computing system is a third party in the unified trust protocol network. In some embodiments, the computing system is a client node of a second trust protocol instance other than the trust protocol instance in the unified trust network.
[079] The UBCDN message can be, for example, the UBCDN message (440) as described in relation to Figure 4. The UBCDN message includes a UBCDN from the trust protocol instance, a digital signature from a UBCDN owner at the UBCDN; and a UBCDN domain certificate.
[080] The trust protocol instance UBCDN includes a trust protocol domain trust name, where the trust domain name is a unique identifier of the trust instance on a network unified trust protocol including a number of trust protocol instances that are communicatively linked by two or more relays. The domain name of the trust protocol includes a human-readable marker and a chain identifier of the trust protocol instance corresponding exclusively to the domain name of the trust protocol.
[081] In some embodiments, the UBCDN domain certificate includes the trust protocol domain name of the trust protocol instance, the public key of the UBCDN owner, and a
Petition 870190056948, of 6/19/2019, p. 39/66
32/44 CA digital signature on the trust protocol domain name of the trust protocol instance and the public key of the UBCDN owner.
[082] In (620), the computing system checks whether the UBCDN domain certificate is issued by a trusted certification authority (CA) using a public key from the certification authority. In some embodiments, the digital signature of the certification authority is obtained by signing the certification authority in the domain name of the trust protocol of the trust protocol instance and by the public key of the UBCDN owner using a private key from the certification authority. certificate corresponding to the public key of the certification authority. In some embodiments, verifying that the UBCDN domain certificate is issued by a trusted certification authority using a public key from the certification authority, includes verifying that the UBCDN domain certificate is issued by the CA using the domain certificate, the CA digital signature and the CA public key.
[083] In (630), in response to the verification that the UBCDN domain certificate is issued by the CA, the computing system checks whether the UBCDN is issued by the UBCDN owner using a public key from the UBCDN owner. In some embodiments, the UBCDN owner 's digital signature is obtained by the UBCDN owner by signing the UBCDN using a private key corresponding to the public key of the UBCDN owner. In some embodiments, verifying that the UBCDN of the trust protocol instance is issued by the UBCDN owner using a public key from the UBCDN owner, including verifying that UBCDN is issued by the UBCDN owner using UBCDN, the digital signature of the UBCDN owner, and the public key of the UBCDN owner. For example, the UBCDN owner can sign the
Petition 870190056948, of 6/19/2019, p. 40/66
33/44
UBCDN using the owner's private key and generate a digital signature, for example, according to a signed algorithm. The computing system as a recipient of the UBCDN message can determine whether the UBCDN is issued by the UBCDN owner using the UBCDN, the digital signature and the owner's public key, for example, according to a signature verification algorithm.
[084] In (640), in response to verifying that the UBCDN is issued by the UBCDN owner, the computing system performs cross-chain transactions between the trust instance and the second trust protocol instance based on the name domain of the trust protocol of the trust protocol instance, for example, according to the process example (500) as described in relation to Figure 5.
[085] Figure 7 illustrates a process example (700) of a UBCDN owner of a trust protocol instance (a UBCDN owner), according to embodiments of the present invention. In some embodiments, the process example (700) can be performed using one or more computer executable programs executed using one or more computing devices. For clarity of presentation, the following description generally describes the process (700) in the context of the other figures in this description. For example, the process example (700) can be performed by the UBCDN owner (430) as described in relation to Figure 4. However, it will be understood that the process (700) can be performed, for example, by any system, appropriate environment, software and hardware, or a combination of systems, environments, software and hardware, as appropriate. In some embodiments, several process steps (700) can be performed in parallel, in combination, in loops or in any order.
[086] In (710), an UBCDN owner of an instance
Petition 870190056948, of 6/19/2019, p. 41/66
34/44 of trust protocol (a UBCDN owner, like the UBCDN owner (430)) obtains a domain certificate (for example, CA (410)) from a trusted certification authority (for example, example, the UBCDN domain certificate (420) of the trust protocol instance. The UBCDN of the trust instance includes a trust protocol domain name of the trust instance and a chain identifier of the trust instance corresponding exclusively to the trust domain name. The UBCDN can be, for example, UBCDN (300), as described in Figure 3. The trust domain name is a unique identifier of the trust protocol instance in a unified trust network, including a number of trust protocol instances that are communicatively linked by two or more relays. In some embodiments, the domain name of the trust protocol includes a human-readable marker. The string identifier indicates a trust network configuration of the trust instance.
[087] The UBCDN domain certificate includes the trust protocol domain name of the trust protocol instance, a public key of the UBCDN owner, and a digital signature from the CA on the domain name of the trust protocol instance of the UBCDN. trust protocol and the public key of the UBCDN owner. The UBCDN domain certificate can be, for example, the domain certificate (420), as described in relation to Figure 4 [088] In (720), the UBCDN owner signs the UBCDN of the trust protocol instance, for example example, using the private key of the UBCDN owner, for example, according to a signature algorithm.
[089] In (730), the UBCDN owner publishes a
Petition 870190056948, of 6/19/2019, p. 42/66
35/44 UBCDN message (for example, the UBCDN message (440a or 440b)) from the trust protocol instance. The UBCDN message includes the UBCDN of the trust protocol instance, a digital signature of the UBCDN owner resulting from the UBCDN signature, and the UBCDN domain certificate.
[090] In (740), the UBCDN owner identifies an updated trust chain instance identifier indicating an updated trust protocol network configuration of the trust instance. For example, a change or update to the trust protocol network configuration of the trust instance can occur (for example, due to system update or the physical location of one or more computing devices, such as the genesis). The string identifier can be updated to reflect updating the trust protocol network configuration of the trust instance (for example, updating the hash value of the trust block genesis block). For example, as illustrated in Figure 4, for the same domain name as the trust protocol (442a) “Example chain,” the chain identifier (444a) “Chain identifier V0” has been updated to a chain identifier (454a ) “Chain Identifier V1”, to reflect the change to the trust protocol network configuration of the trust instance.
[091] In (750), the UBCDN owner signs an updated UBCDN from the trust protocol instance, for example, using the private key of the UBCDN owner. The updated UBCDN of the trust instance includes the trust protocol domain name of the trust instance and the updated chain identifier of the trust instance. For example, as illustrated in Figure 4, the
Petition 870190056948, of 6/19/2019, p. 43/66
36/44
Updated UBCDN of the trust protocol instance includes the same domain name as the trust protocol (442a) “Example chain.” And the updated chain identifier (454a) “Chain Identifier V1”.
[092] In (760), the UBCDN owner publishes an updated UBCDN message from the trust protocol instance. The updated UBCDN message includes the updated UBCDN from the trust protocol instance, an updated digital signature from the UBCDN owner resulting from the updated UBCDN signature, and the UBCDN domain certificate. For example, as shown in Figure 4, the UBCDN owner (430a) issues an updated UBCDN message (450a) that includes the trust protocol domain name (442a) “Example chain.” And the updated chain identifier ( 454a) “V1 chain identifier”, a digital signature (456a) and a domain certificate (458a). The domain certificate (458a) can be the domain certificate (420a) issued by the CA (410) and received by the UBCDN owner (430a) from the CA (410). The updated digital signature (456a) may result from the signature by the UBCDN owner (430a) of the updated UBCDN (that is, the domain name of the trust protocol (442a) “Example chain” and the updated chain identifier (454a) “Chain Identifier V0” in this case) using the private key of the UBCDN owner (430a).
[093] Figure 8 illustrates a process example (800) of a relay for cross-chain interactions in a unified trust protocol network, according to embodiments of the present invention. The unified trust protocol network includes multiple trust protocol instances that are communicatively linked by two or more relays. In some embodiments, the process example (800) can be performed using one or more computer executable programs executed using one or more computing devices. For clarity of
Petition 870190056948, of 6/19/2019, p. 44/66
37/44 presentation, the following description generally describes the process (800) in the context of the other figures in this description. For example, the process example (800), which can be performed by the relay on a unified trust protocol network. However, it will be understood that the process (800) can be performed, for example, by any suitable system, environment, software and hardware, or a combination of systems, environments, software and hardware, as appropriate. For example, the relay can be a node (for example, the computing system (106) or (108) as described in relation to Figure 1 or the node (214) as described in relation to Figure 2), a protocol instance trust (for example, a trust protocol network (102) or the trust protocol network (212)), or another computer system in the unified trust protocol network. In some embodiments, several process steps (800) can be performed in parallel, in combination, in loops or in any order.
[094] In (810), the relay, which is communicatively linked to a first trust protocol instance and a second trust protocol instance in the unified trust network, identifies a domain name of the trust protocol trust of a first instance of trust protocol. The trust protocol domain name of a first trust protocol instance is a unique identifier of a first trust protocol instance and uniquely corresponds to a chain identifier of a first trust protocol instance in the unified trust network . In some embodiments, the trust protocol domain name of a first trust protocol instance includes a first human-readable marker.
[095] In (820), the relay identifies a trust protocol domain name from the second trust protocol instance. The domain name of the second protocol instance trust protocol
Petition 870190056948, of 6/19/2019, p. 45/66
38/44 trust is a unique identifier of the second trust protocol instance and uniquely corresponds to a chain identifier of the second trust protocol instance in the unified trust network. In some embodiments, the trust protocol domain name of the second trust protocol instance includes a second human-readable marker.
[096] In some embodiments, a relay may designate a local identifier for each trust protocol that is communicatively linked. The local identifier is designated for the use of the relay and cannot be used by other nodes or relays in the unified trust protocol network. In some embodiments, identifying a trust protocol domain name from a first trust protocol instance includes using the trust protocol domain name from a first trust protocol instance as the local identifier of a first trust protocol instance or replace the local identifier of a first trust protocol instance with the trust protocol domain name of a first trust protocol instance. Likewise, identifying a trust protocol domain name from the second trust protocol instance includes using the trust protocol domain name from the second trust protocol instance as the local identifier of the second trust protocol instance. trust or the replacement of the unique identifier of the second trust protocol instance with the domain name of the trust protocol of the second trust protocol instance.
[097] At (830), the relay receives an access request to access the second instance of the trust protocol. The access request includes the domain name of the trust protocol of the second trust protocol instance.
Petition 870190056948, of 6/19/2019, p. 46/66
39/44 [098] In (840), the relay identifies the chain identifier of the second trust protocol instance based on the trust protocol domain name of the second trust protocol instance. The chain identifier of the second trust instance indicates a trust network configuration of the second trust instance.
[099] In some embodiments, identification of the second trust protocol instance string identifier based on the second trust protocol instance trust protocol domain name includes the identification of the second instance trust chain identifier trust protocol, according to the query information stored locally in the relay based on the domain name of the trust protocol.
[0100] In some embodiments, identifying the second protocol trust chain string identifier based on the second trust protocol instance trust protocol domain name includes the second protocol instance chain identifier trust based on the trust protocol domain name of the second trust protocol instance from a remote unified trust domain name server.
[0101] In (850), the relay provides access to the second trust protocol instance for a first trust protocol instance based on the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance. In some embodiments, the relay provides access to the second instance of the trust protocol for a first instance of the trust protocol according to a communication protocol designed for cross-chain interactions. For example, the relay can load the network configuration from
Petition 870190056948, of 6/19/2019, p. 47/66
40/44 trust protocol indicated by the chain identifier of the second trust protocol instance corresponding to the domain name of the trust protocol of the second trust protocol instance. The relay uses the trust protocol network configuration to connect to the second trust protocol instance, obtains a requested result via a first trust protocol instance from the second trust protocol instance, and returns the requested result via a first instance of trust protocol to a first instance of trust protocol, for example, according to the examples of techniques described in relation to Figure 5.
[0102] In some embodiments, providing, through the relay, access to the second instance of trust protocol for a first instance of trust protocol based on the trust protocol network configuration indicated by the chain identifier of the second instance of trust Trust protocol includes providing, through the relay, access to the second instance of the trust protocol to a first instance of the trust protocol through a second relay.
[0103] In some embodiments, the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance is identified by the second relay based on the same chain identifier as the second trust protocol instance. In some embodiments, the second trust protocol instance is accessed by the second relay based on the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance. In other words, a first trust protocol instance can use the same domain name as the second trust protocol instance, regardless of which relay it is, or how many relays are used to interact with the second trust protocol instance.
Petition 870190056948, of 6/19/2019, p. 48/66
41/44 trust protocol.
[0104] In some embodiments, the trust protocol network configuration indicated by the chain identifier of the second trust protocol instance is identified by the second relay according to the search information stored locally in the second relay based on the same identifier string of the second trust protocol instance.
[0105] In some embodiments, the trust network configuration indicated by the chain identifier of the second trust protocol instance is identified by the second relay based on the trust protocol domain name of the second trust protocol instance of a unified domain name of remote trust protocol server.
[0106] The described features can be implemented in digital electronic circuits or in computer hardware, firmware, software or combinations thereof. The apparatus can be implemented in a computer program product tangibly incorporated in an information vehicle (for example, in a machine-readable storage device) for realization by a programmable processor; and the steps of the method can be performed by a programmable processor executing an instruction program to execute functions of the described embodiments operating on the input data and generating the output. The described features can be advantageously implemented in one or more computer programs that are executable in a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device and at least one output device. A computer program is a set of
Petition 870190056948, of 6/19/2019, p. 49/66
42/44 instructions that can be used, directly or indirectly, on a computer to perform a certain activity or obtain a certain result. A computer program can be written in any form of programming language, including compiled or interpreted languages, and can be implemented in any way, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.
[0107] Processors suitable for carrying out an instruction program include, for example, microprocessors for general and special use, and the single processor or one of multiple processors of any type of computer. Generally, a processor will receive instructions and data from either a read-only memory or a random access memory or both. The elements of a computer can include a processor to execute instructions and one or more memories to store instructions and data. Generally, a computer can also include, or is operationally attached to communicate with, one or more mass storage devices to store data files; such devices include magnetic disks, such as internal hard drives and removable disks; magneto-optical discs; and optical discs. Storage devices suitable for tangibly incorporating computer program instructions and data include all forms of non-volatile memory, including, for example, semiconductor memory devices, such as EPROM, EEPROM and flash memory devices; magnetic disks, such as internal hard drives and removable disks; magneto-optical discs; and CD-ROM and DVD-ROM discs. The processor and memory can be supplemented by, or incorporated into, application-specific integrated circuits (ASICs).
[0108] To provide interaction with a user, the
Petition 870190056948, of 6/19/2019, p. 50/66
43/44 features can be implemented on a computer with a display device, such as a cathode ray tube (CRT) or liquid crystal display (LCD) monitor to display information to the user and a keyboard and pointing device, such as a mouse or a trackball, through which the user can provide input to the computer.
[0109] Features can be implemented on a computer system that includes an administrative panel component (back-end), such as a data server, or that includes a middleware component, such as an application server or an Internet server , or that includes a front-end user interface component, such as a client computer with a graphical user interface or an Internet browser, or any combination thereof. The system components can be connected by any form or means of digital data communication, such as a communication network. Examples of communication networks include, for example, a local area network (LAN), a wide area network (WAN) and the computers and networks that make up the Internet.
[0110] The computer system can include clients and servers. A client and a server are usually remote with each other and usually interact over a network, as described. The client and server relationship arises because of computer programs running on the respective computers and having a client-server relationship between them.
[0111] In addition, the logical flows represented in the figures do not require the particular order shown, or sequential order, to achieve the desired results. In addition, other steps can be provided, or steps can be eliminated, from the described flows, and other components can be added or removed from the described systems. Therefore, other embodiments are within the scope of the following claims.
Petition 870190056948, of 6/19/2019, p. 51/66
44/44 [0112] A number of embodiments of the present invention have been described. However, it will be understood that various modifications can be made without departing from the scope of the present invention. Therefore, other embodiments are within the scope of the following claims.

权利要求:
Claims (10)
[1]
Claims
1. METHOD (800) IMPLEMENTED BY A COMPUTER'S RELAY FOR CROSS-CHAIN INTERACTIONS IN A UNIFIED CONFIDENCE PROTOCOL NETWORK (212) comprising a plurality of trust protocol instances that are communicatively linked by two or more relays, characterized by the fact that method (800) comprises:
identify (810), through the relay that is communicatively linked to a first instance of trust protocol and a second instance of trust protocol in the unified trust network (212), a domain name of the trust protocol of a first trust protocol instance, where the trust protocol domain name of the first trust protocol instance is a unique identifier of the first trust protocol instance and uniquely matches a chain identifier of the first trust instance trust protocol in the unified trust protocol network (212);
identify (820), through the relay, a domain name of the trust protocol of the second instance of trust protocol, where the domain name of the trust protocol of the second instance of trust protocol is a unique identifier of the second instance of trust trust protocol and uniquely corresponds to a chain identifier of the second trust protocol instance in the unified trust protocol network (212);
receive (830), through the relay from a node (214) of the first trust protocol instance, an access request to access the second trust protocol instance, where the access request comprises the domain name of the second confidence protocol
Petition 870190056948, of 6/19/2019, p. 53/66
[2]
2/5 instance of trust protocol;
identify (840), through the relay, the chain identifier of the second trust protocol instance based on the domain name of the trust protocol of the second trust protocol instance, where the chain identifier of the second trust protocol instance trust indicates a trust protocol network configuration (212) of the second trust protocol instance; and provide (850), through the relay, access to the second trust protocol instance for the first trust protocol instance based on the trust protocol network configuration (212) indicated by the chain identifier of the second trust protocol instance. confidence.
2. METHOD (800), according to claim 1, characterized by the fact that:
identifying a trust protocol domain name from the first trust protocol instance includes using the trust protocol domain name from the first trust protocol instance as a local identifier from the first trust protocol instance; and the identification of a trust protocol domain name of the second trust protocol instance comprises the use of the trust protocol domain name of the second trust protocol instance as a local identifier of the second trust protocol instance.
[3]
3. METHOD (800), according to claim 1, characterized by the fact that identifying the chain identifier of the second instance of trust protocol based on the domain name of the trust protocol of the second instance of trust protocol comprises identifying the string identifier of the second instance of
Petition 870190056948, of 6/19/2019, p. 54/66
3/5 trust protocol according to query information stored locally in the relay based on the domain name of the trust protocol.
[4]
4. METHOD (800), according to claim 1, characterized by the fact that identifying the chain identifier of the second instance of trust protocol based on the domain name of the trust protocol of the second instance of trust protocol comprises identifying the string identifier of the second trust protocol instance based on the trust protocol domain name of the second trust protocol instance from a remote unified trust domain name server.
[5]
5. METHOD (800), according to claim 1, characterized by the fact that the supply, through the relay, of access to the second instance of trust protocol for the first instance of trust protocol based on the network configuration of trust protocol (212) indicated by the chain identifier of the second trust protocol instance comprises providing, through the relay, access to the second trust protocol instance for the first trust protocol instance via a second relay;
wherein the trust protocol network configuration (212) indicated by the chain identifier of the second trust protocol instance is identified by the second relay based on the same chain identifier as the second trust protocol instance; and wherein the second trust protocol instance is accessed by the second relay based on the trust protocol network configuration (212) indicated by the chain identifier of the second trust protocol instance.
[6]
6. METHOD (800), according to claim 4, characterized by the fact that the network configuration of
Petition 870190056948, of 6/19/2019, p. 55/66
4/5 trust (212) indicated by the chain identifier of the second trust protocol instance is identified by the second relay according to the search information stored locally in the second relay based on the same chain identifier of the second trust protocol instance .
[7]
7. METHOD (800), according to claim 4, characterized by the fact that the trust protocol network configuration (212) indicated by the chain identifier of the second trust protocol instance is identified by the second relay based on the trust protocol domain name of the second trust protocol instance from a remote unified trust domain name server.
[8]
8. METHOD (800), according to claim 1, characterized by the fact that the domain name of the trust protocol of the first instance of trust protocol comprises a first human-readable marker; and the trust protocol domain name of the second trust protocol instance comprises a second human-readable marker.
[9]
9. LEGIBLE STORAGE MEDIA BY COMPUTER, NON-TRANSITIONAL, characterized by the fact that it is coupled to one or more processors and has instructions stored in it that, when executed by one or more processors, cause the one or more processors to perform operations according to the method (800), as defined in any one of claims 1 to 8.
[10]
10. SYSTEM (106, 108), characterized by the fact that it includes: a computer device; and a computer-readable storage device attached to the computer device and having instructions stored on it that, when executed by the computer device, cause
Petition 870190056948, of 6/19/2019, p. 56/66
5/5 that the computer device performs operations according to method (800), as defined in any one of claims 1 to 8.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019007991A2|2019-09-10|computer-implemented method of a relay for cross-chain interactions in a unified trusted protocol network, computer readable, non-transient storage media, and system

---

BR112019008000A2|2019-09-10|computer-implemented method for authenticating a domain name, storage medium, and system

---

BR112019008025A2|2019-09-10|computer-implemented method, non-transient computer-readable storage medium, and system

同族专利:

---

公开号 | 公开日

---

US20210281429A1|2021-09-09|

---

ZA201902480B|2021-02-24|

---

US11025438B2|2021-06-01|

---

MX2019004650A|2019-08-05|

---

JP2020503583A|2020-01-30|

---

EP3549325A2|2019-10-09|

---

JP6699861B2|2020-05-27|

---

AU2020204535B2|2021-04-29|

---

KR20200059185A|2020-05-28|

---

EP3549325A4|2020-01-08|

---

CA3041208C|2021-05-04|

---

SG11201903496PA|2019-05-30|

---

KR102125659B1|2020-06-23|

---

US11212114B2|2021-12-28|

---

US20200280453A1|2020-09-03|

---

RU2708350C1|2019-12-05|

---

US10666445B2|2020-05-26|

---

CA3041208A1|2019-04-18|

---

EP3549325B1|2021-07-07|

---

US20190253263A1|2019-08-15|

---

CN110268677A|2019-09-20|

---

AU2018347193B2|2020-05-14|

---

PH12019500878A1|2019-11-25|

---

WO2019072273A3|2019-09-12|

---

PH12019500878B1|2019-11-25|

---

WO2019072273A2|2019-04-18|

---

AU2020204535A1|2020-07-30|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US6502135B1|1998-10-30|2002-12-31|Science Applications International Corporation|Agile network protocol for secure communications with assured system availability|

---

US7418504B2|1998-10-30|2008-08-26|Virnetx, Inc.|Agile network protocol for secure communications using secure domain names|

---

KR101029364B1|2008-06-24|2011-04-13|주식회사 케이티|Mobile terminal unit for providing integrated web browsing service, mobile communication system, local area wireless communication system and method thereof|

---

TWI523471B|2014-03-27|2016-02-21|國立臺北科技大學|Method of transmitting by relay server for advanced domain name system|

---

US10230526B2|2014-12-31|2019-03-12|William Manning|Out-of-band validation of domain name system records|

---

WO2017122187A2|2016-01-15|2017-07-20|Enrico Maim|Methods and systems implemented in a network architecture with nodes capable of performing message-based transactions|

---

US10484168B2|2015-03-02|2019-11-19|Dell Products L.P.|Methods and systems for obfuscating data and computations defined in a secure distributed transaction ledger|

---

JP2018516026A|2015-03-20|2018-06-14|リヴェッツ・コーポレーションＲｉｖｅｔｚ Ｃｏｒｐ．|Automatic device integrity authentication using blockchain|

---

KR20160124294A|2015-04-16|2016-10-27|삼성전자주식회사|Semiconductor device including cell region stacked on periperal region and methods for fabricating the same|

---

US9870562B2|2015-05-21|2018-01-16|Mastercard International Incorporated|Method and system for integration of market exchange and issuer processing for blockchain-based transactions|

---

KR20160137793A|2015-05-21|2016-12-01|삼성전자주식회사|3-dimsional semiconductor memory device and operation method thereof|

---

US10963881B2|2015-05-21|2021-03-30|Mastercard International Incorporated|Method and system for fraud control of blockchain-based transactions|

---

US10084794B2|2015-06-02|2018-09-25|ALTR Solutions, Inc.|Centralized access management of web-based or native applications|

---

US10346826B2|2015-07-28|2019-07-09|Wesley John Boudville|Blockchain and deep links for mobile apps|

---

EP3193299A1|2016-01-15|2017-07-19|Accenture Global Services Limited|Device, method and system for autonomous selection of a commodity supplier through a blockchain distributed database|

---

US9853047B2|2016-01-26|2017-12-26|SK Hynix Inc.|Semiconductor device and method of manufacturing the same|

---

US20170236123A1|2016-02-16|2017-08-17|Blockstack Inc.|Decentralized processing of global naming systems|

---

WO2017145049A1|2016-02-23|2017-08-31|nChain Holdings Limited|Consolidated blockchain-based data transfer control method and system|

---

EP3420514A1|2016-02-23|2019-01-02|Nchain Holdings Limited|A method and system for securing computer software using a distributed hash table and a blockchain|

---

WO2017164784A1|2016-03-24|2017-09-28|Telefonaktiebolaget Lm Ericsson |Data object transfer between network domains|

---

US9855785B1|2016-04-04|2018-01-02|Uipco, Llc|Digitally encoded seal for document verification|

---

US20170302663A1|2016-04-14|2017-10-19|Cisco Technology, Inc.|BLOCK CHAIN BASED IoT DEVICE IDENTITY VERIFICATION AND ANOMALY DETECTION|

---

US11223598B2|2016-05-03|2022-01-11|Nokia Of America Corporation|Internet security|

---

JP6628188B2|2016-05-10|2020-01-08|日本電信電話株式会社|Payment system, payment method, transaction generation device, and transaction generation program|

---

WO2017218983A1|2016-06-16|2017-12-21|The Bank Of New York Mellon|Distributed, centrally authored block chain network|

---

EP3476102B1|2016-06-24|2020-06-17|Innogy Innovation Gmbh|Augmented reality system|

---

WO2018006945A1|2016-07-05|2018-01-11|Rwe International Se|Observation system|

---

CN106210171A|2016-07-25|2016-12-07|宁圣金融信息服务（上海）有限公司|A kind of block chain domain name analysis system|

---

US10860735B2|2016-08-05|2020-12-08|Sensoriant, Inc.|Database system for protecting and securing stored data using a privacy switch|

---

US10361869B2|2016-08-23|2019-07-23|International Business Machines Corporation|Event ledger|

---

US10339014B2|2016-09-28|2019-07-02|Mcafee, Llc|Query optimized distributed ledger system|

---

US11182851B2|2016-10-20|2021-11-23|International Business Machines Corporation|Inter-ledger messaging in a blockchain|

---

CN106991334B|2016-11-24|2021-03-02|创新先进技术有限公司|Data access method, system and device|

---

US10686590B2|2016-12-23|2020-06-16|Joseph Santilli|Methods and systems for crowdsourcing an outcome to an issue|

---

US10164983B2|2017-01-20|2018-12-25|Verizon Patent And Licensing Inc.|Distributed authentication for internet-of-things resources|

---

RU2639015C1|2017-01-26|2017-12-19|Игорь Сан-Сенович Дю|Authenticity and quality control procedure of production in the process of manufacture and implementation|

---

US9992022B1|2017-02-06|2018-06-05|Northern Trust Corporation|Systems and methods for digital identity management and permission controls within distributed network nodes|

---

JP6341491B1|2017-02-21|2018-06-13|株式会社三菱Ｕｆｊ銀行|Signal processing method and signal processing program|

---

CN106960388A|2017-03-01|2017-07-18|中钞信用卡产业发展有限公司北京智能卡技术研究院|The method and apparatus of the digital asset circulation of transregional piece of chain|

---

US11196573B2|2017-03-06|2021-12-07|Nokia Technologies Oy|Secure de-centralized domain name system|

---

AU2018230763A1|2017-03-08|2019-10-31|Ip Oversight Corporation|System and method for creating commodity asset-secured tokens from reserves|

---

CN107196900B|2017-03-24|2020-04-24|创新先进技术有限公司|Consensus checking method and device|

---

US10848322B2|2017-03-24|2020-11-24|Cable Television Laboratories, Inc|System and method for distributed PKI root|

---

JP6904002B2|2017-03-30|2021-07-14|ソニーグループ株式会社|Information processing device and information processing method|

---

WO2018176406A1|2017-03-31|2018-10-04|北京大学深圳研究生院|Top-level domain name management method and system based on alliance chain|

---

US11095432B2|2017-04-05|2021-08-17|Samsung Sds Co., Ltd.|System for processing data based on blockchain and operating method thereof|

---

US10102265B1|2017-04-12|2018-10-16|Vijay K. Madisetti|Method and system for tuning blockchain scalability for fast and low-cost payment and transaction processing|

---

US10412045B1|2017-04-17|2019-09-10|Verisign, Inc.|Domain name registration reservation through the use of encoding domain names for pools|

---

US20190166085A1|2017-04-19|2019-05-30|Peking University Shenzhen Graduate School|Blockchain-based domain name resolution system|

---

US10320574B2|2017-05-05|2019-06-11|International Business Machines Corporation|Blockchain for open scientific research|

---

US20190012660A1|2017-07-06|2019-01-10|Robert Masters|Systems and methods for providing an architecture for an internet-based marketplace|

---

CN107566337B|2017-07-26|2019-08-09|阿里巴巴集团控股有限公司|Communication means and device between a kind of block chain node|

---

CN107592292B|2017-07-26|2019-08-09|阿里巴巴集团控股有限公司|A kind of block chain communication method between nodes and device|

---

US20190066068A1|2017-08-22|2019-02-28|Sap Se|Transaction Platform Providing Unified Interaction with Multiple Heterogeneous Blockchains|

---

US10938567B2|2017-09-12|2021-03-02|Kadena Llc|Parallel-chain architecture for blockchain systems|

---

WO2019056006A1|2017-09-18|2019-03-21|James Leftwich|Method for producing a dynamically ordered queue|

---

CN107613041B|2017-09-22|2020-06-05|中国互联网络信息中心|Domain name management system, domain name management method and domain name resolution method based on block chain|

---

US10958418B2|2017-10-10|2021-03-23|Chromata Corporation|System and method for a blockchain network with heterogeneous privacy|

---

US20190116038A1|2017-10-12|2019-04-18|Rivetz Corp.|Attestation With Embedded Encryption Keys|

---

US11121870B2|2017-10-12|2021-09-14|Mastercard International Incorporated|Method and system for interacting public and private blockchains with controlled participation|

---

CN107888562B|2017-10-13|2019-12-27|布比（北京）网络技术有限公司|Data verification and transceiving method, node and system for parallel link access to interconnection chain|

---

CN107911421B|2017-10-30|2020-05-15|上海点融信息科技有限责任公司|Method, apparatus, and computer storage medium for configuring cross-network communications in a blockchain|

---

WO2019109003A1|2017-11-30|2019-06-06|Visa International Service Association|Blockchain system for confidential and anonymous smart contracts|

---

KR20190067581A|2017-12-07|2019-06-17|한국전자통신연구원|Apparatus and method for distributed processing of blockchain transactions|

---

WO2019114934A1|2017-12-12|2019-06-20|Motorola Mobility Llc|Providing network access using blockchain payments|

---

CN108418795B|2018-01-30|2019-05-28|百度在线网络技术（北京）有限公司|Data access method, device, system and the computer-readable medium of transregional piece of chain|

---

CN108347486A|2018-02-12|2018-07-31|众安信息技术服务有限公司|Across chain communication means, device and system based on block chain|

---

US20190251199A1|2018-02-14|2019-08-15|Ivan Klianev|Transactions Across Blockchain Networks|

---

CN108415784B|2018-02-27|2020-04-24|阿里巴巴集团控股有限公司|Cross-block-chain interaction method, device, system and electronic equipment|

---

CN108683630B|2018-04-03|2020-05-29|阿里巴巴集团控股有限公司|Cross-block-chain authentication method and device and electronic equipment|

---

CN108712257B|2018-04-03|2020-04-17|阿里巴巴集团控股有限公司|Cross-block-chain authentication method and device and electronic equipment|

---

JP2019185296A|2018-04-06|2019-10-24|富士通株式会社|Data managing device, data managing program and data managing method|

---

US11132707B2|2018-04-25|2021-09-28|At&T Intellectual Property I, L.P.|Blockchain solution for an automated advertising marketplace|

---

CN108665365B|2018-05-16|2021-07-13|四川大学|Mixed block chain architecture system, processing method and processing system|

---

CN108712506B|2018-05-31|2021-02-02|中国联合网络通信集团有限公司|Block chain node communication method and device and block chain node|

---

US10505718B1|2018-06-08|2019-12-10|Cisco Technology, Inc.|Systems, devices, and techniques for registering user equipment in wireless networks using a native blockchain platform|

---

US10673618B2|2018-06-08|2020-06-02|Cisco Technology, Inc.|Provisioning network resources in a wireless network using a native blockchain platform|

---

US11196551B2|2018-06-27|2021-12-07|International Business Machines Corporation|Automated task management on a blockchain based on predictive and analytical analysis|

---

US20200050690A1|2018-08-07|2020-02-13|International Business Machines Corporation|Preservation of uniqueness and integrity of a digital asset|

---

US20190050854A1|2018-09-28|2019-02-14|Intel Corporation|Blockchain-based digital data exchange|

---

US11093479B2|2018-11-06|2021-08-17|Workday, Inc.|Ledger data generation and storage for trusted recall of professional profiles|

---

AU2018347192B2|2018-11-16|2020-06-25|Advanced New Technologies Co., Ltd.|A domain name management scheme for cross-chain interactions in blockchain systems|

---

AU2018348320B2|2018-11-16|2020-01-16|Advanced New Technologies Co., Ltd.|A domain name scheme for cross-chain interactions in blockchain systems|

---

CA3041208C|2018-11-16|2021-05-04|Alibaba Group Holding Limited|Cross-chain interactions using a domain name scheme in blockchain systems|CA3041208C|2018-11-16|2021-05-04|Alibaba Group Holding Limited|Cross-chain interactions using a domain name scheme in blockchain systems|

---

AU2018347192B2|2018-11-16|2020-06-25|Advanced New Technologies Co., Ltd.|A domain name management scheme for cross-chain interactions in blockchain systems|

---

CN111899104A|2018-11-27|2020-11-06|创新先进技术有限公司|Service execution method and device|

---

US10901983B2|2019-03-01|2021-01-26|Wanchain Ltd.|System and method for universal blockchain interoperability|

---

US11151276B1|2019-04-15|2021-10-19|Trend Micro Incorporated|Systems and methods for data certificate notarization utilizing bridging from private blockchain to public blockchain|

---

CN110084601B|2019-04-30|2021-03-16|杭州复杂美科技有限公司|Parallel chain main chain transaction state synchronization method, equipment and storage medium|

---

CN110417742B|2019-06-28|2020-11-06|创新先进技术有限公司|Method, device and storage medium for cross-link sending, transferring and receiving authenticable message|

---

US10742415B2|2019-06-28|2020-08-11|Alibaba Group Holding Limited|Method and apparatus for inter-blockchain transmission of authenticable message|

---

CN110471984B|2019-07-15|2020-08-25|阿里巴巴集团控股有限公司|Service processing method and device based on block chain and electronic equipment|

---

US10937096B2|2019-07-15|2021-03-02|Advanced New Technologies Co., Ltd.|Transaction processing in a service blockchain|

---

US11196771B2|2019-07-16|2021-12-07|International Business Machines Corporation|Multi-domain blockchain network with data flow control|

---

CN110650189B|2019-09-20|2022-01-18|深圳供电局有限公司|Relay-based block chain interaction system and method|

---

CN110944058B|2019-12-04|2022-03-04|杭州复杂美科技有限公司|Block chain intranet node relay connection method|

---

CN110933189A|2020-02-10|2020-03-27|北京启迪区块链科技发展有限公司|Fabric-based block chain network deployment method, device, equipment and medium|

---

WO2021190740A1|2020-03-25|2021-09-30|NEC Laboratories Europe GmbH|Bootstrapping root of trust for federated blockchains|

---

CN112380294B|2020-12-31|2021-04-06|支付宝信息技术有限公司|Block chain cross-chain access method and device|

法律状态:
2021-04-20| B25A| Requested transfer of rights approved|Owner name: ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD. (KY) |

---

2021-05-11| B25A| Requested transfer of rights approved|Owner name: ADVANCED NEW TECHNOLOGIES CO., LTD. (KY) |

---

2021-10-05| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

PCT/CN2018/115926|WO2019072273A2|2018-11-16|2018-11-16|Cross-chain interactions using a domain name scheme in blockchain systems|

---